Avoid including null values in blocks list #41496
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
The problem reported in #41263 seems to be caused because of the inclusion of a
null
value in the list of blocks returned bygetBlocks
.This small change will prevent having a
null
when the code is not running on a WP Context.Why?
fixes #41263
How?
It avoids having
null
values in the list of blocksTesting Instructions
npm run storybook:dev
Playground/Block editor/Default
storyScreenshots or screencast
Before:
After: